-
Notifications
You must be signed in to change notification settings - Fork 12k
feat(@angular/cli): disable progress when running outside TTY #8501
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
The default value is changed from `true` to `progress.stdout.isTTY`. It still has lower priority than value specified by command line flag or in the .angular-cli.json config. Fixes angular#8148
2681fde
to
428835e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a really nice feature, thanks!
…de TTY Fixes a shortcoming of angular#8501. Apply same logic for setting --progress flat when running Karma directly (as opposed to running it using `ng test` command). Fixes angular#8148
…de TTY Fixes a shortcoming of angular#8501. Apply same logic for setting --progress flag when running Karma directly (as opposed to running it using `ng test` command). Fixes angular#8148
…de TTY Fixes a shortcoming of angular#8501. Apply same logic for setting --progress flag when running Karma directly (as opposed to running it using `ng test` command). Fixes angular#8148
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
The default value is changed from
true
toprogress.stdout.isTTY
. Itstill has lower priority than value specified by command line flag or in
the .angular-cli.json config.
Fixes #8148
Not sure how to add a test though... Verified manually using: